network architecture having multicast and broadcast multimedia subsystem capabilities

专利摘要:
the present invention relates to examples of network architectures. some network architectures comprise a central network (cn) subarchitecture and a multicast service center (bm-sc) subarchitecture. some network architecture comprises a cn that implements the functionality of bm-sc. the architectures comprise network functions and interfaces between some of the network functions that allow messages and transmissions from the multicast multimedia transmission system (mbms).
公开号:BR112019013865A2
申请号:R112019013865
申请日:2018-01-04
公开日:2020-04-14
发明作者:Dung Dao Ngoc
申请人:Huawei Tech Co Ltd；
IPC主号:

专利说明:

Descriptive Report of the Patent for ’'NETWORK ARCHITECTURE HAVING MULTICAST AND BROADCAST MULTIMEDIA SUBSYSTEM CAPACITIES”.
CROSS REFERENCE TO RELATED APPLICATIONS [0001] This application claims priority benefit for US Provisional Patent Application No. 62/442 .644 filed on January 5, 2017 and entitled “Network Architecture Having Multicast and Broadcast Multimedia Subsystem Capabilities” and US Patent Application with serial number 15 / 861,096 filed on January 3, 2018 and entitled Network Architecture Having Multicast and Broadcast Multimedia Subsystem Capabilities, which are incorporated by reference as if they were reproduced in their entirety.
FIELD OF THE INVENTION [0002] The present invention belongs to the field of network communications and, in particular, to a network architecture having multicast and broadcast multimedia subsystem (MBMS) capabilities.
BACKGROUND [0003] The multicast and broadcast multimedia subsystem (MBMS) features were developed for third generation (3G) and fourth generation (4G) networks. Current MBMS applications include television broadcasting, unicast video streaming, vehicular applications for transmitting traffic messages and a public safety / warning transmission system. Currently, there is no known fifth generation (5G) network architecture with multicast capabilities and a multimedia broadcast subsystem (MBMS).
[0004] This background information is provided to reveal the information believed by the applicant to be of possible relevance to the present invention. No admission is necessarily intended, nor should it be construed, that any preceding information constitutes the prior art against the present invention.
Petition 870190077600, of 8/12/2019, p. 21/69
2/41
SUMMARY [0005] An objective of the modalities of the present invention is to provide a network architecture having capabilities of the multicast and broadcast multimedia subsystem (MBMS).
[0006] In accordance with the modalities of the present invention, a network architecture is provided. The network architecture comprises a central network (CN) and a broadcast-multicast service center (BMSC). The CN comprises an authentication server function (AUSF) and a network exposure function (NEF) that are communicated via an NG AUSF-NEF interface. The BM-SC comprises a safety function that is communicated to the NEF via an NG MBMS-NEF interface.
[0007] In accordance with the modalities of the present invention, yet another network architecture is provided. The network architecture comprises a CN and BM-SC. The CN comprises an AUSF, a NEF and a policy control function (PCF). AUSF and NEF are communicated via an NG AUSF-NEF interface. NEF and PCF are connected via an NG PCF-NEF interface. The BM-SC comprises a member function that is communicated to the NEF via an NG MBMS-NEF interface. The member function is further communicated to the PCF via an NG5 interface.
[0008] In accordance with the modalities of the present invention, yet another network architecture is provided. The network architecture comprises a CN and a BM-SC. The CN comprises an AUSF, a NEF and a policy control function (PCF). AUSF and NEF are communicated via an NG AUSF-NEF interface. NEF and PCF are connected via an NG PCF-NEF interface. BM-SC comprises a member function and a
Petition 870190077600, of 8/12/2019, p. 22/69
3/41 security function. The member function is communicated to the NEF via an NG MBMS-NEF interface. The member function is further communicated to the PCF via an NG5 interface. The safety function is communicated to the NEF via an NG MBMS-NEF interface.
[0009] In accordance with the modalities of the present invention, a network architecture is also provided. The network architecture comprises a BM-SC and a CN. BM-SC comprises a transport and proxy function, a service announcement function, and a session and transmission function. The session and transmission function is communicably connected to each transport and proxy function and the service announcement function. The CN comprises the flat user function (UPF) which is connected to the transport and proxy function through a first NG6-MBMS interface. The UPF is further connected to the service announcement function via a second NG6-MBMS interface. A transmission from the multicast and broadcast multimedia subsystem (MBMS) received in the session and transmission function is forwarded to the transport and proxy function. The MBMS transmission is then forwarded via the NG6-MBMS interface to the UPF. The MBMS transmission is then forwarded to an access node (AN) via an NG3-MBMS interface.
[0010] In accordance with the modalities of the present invention, a method is also provided for providing access to an MBMS transmission. The method comprises an AUSF in a CN receiving a security code from an MBMS security function from a BMSC and sending the security code to user equipment (UE). AUSF receives the security code of an NEF through an NG AUSF-NEF interface. NEF received the security code from the MBMS security function through an NG MBMSNEF interface.
Petition 870190077600, of 8/12/2019, p. 23/69
[0011] In accordance with the modalities of the present invention, a method of transmitting a secure transmission of MBMS is also provided. The method comprises an AUSF by sending a flat user function (UPF) a first security code, and sending a second security code to the UPF. The first security code is to decode an MBMS transmission requested by UE received at LJPF through an NG6-MBMS interface. The second security code is to encode the transmission of MBMS to be sent to an AN over an N3-MBMS interface. The UE is connected to the AN.
[0012] One aspect of the description provides a method for delivering content from a content provider to a plurality of User Equipment (UE) using at least one multicast and broadcast data transmission. Such a method includes receiving, through a function of the authentication server (AUSF) of a central network (CN), a request for an authenticated UE to access content directed to the plurality of UEs. The method further includes receiving security information from the CN's AUSF comprising a decoding code from a security function that provides the decoding code for use by the authenticated UE to decode the content. The method also includes sending, through the CN's AUSF, the decryption code towards the authenticated UE. In some embodiments, sending the decryption code towards the authenticated UE includes sending the decoding code to an access and mobility management (AMF) function for forwarding to the authenticated UE. In some embodiments, sending the decryption code to the authenticated UE via the CN AUSF includes sending the decoding code to the authenticated UE by the AUSF of the CN for forwarding to the authenticated UE via a access and mobility management (AMF) function. In some modalities, the method also includes sending, by CN's AUSF, to a Session Management Function
Petition 870190077600, of 8/12/2019, p. 24/69
5/41 (SMF) a second decoding code for use by a User Plan Function (UPF) in decoding content received by the content provider's UPF, the received content directed to the plurality of UEs; and send SMF a first security code for use by the UPF when encoding the requested content for forwarding towards the plurality of UEs, the first security code corresponding to the decryption code. In some embodiments, the security function is at least one of: instantiated as a central network function with security data stored within the central network, but provided by the content provider; and located outside the central network. In some embodiments, security information is received via another central network function.
[0013] Another aspect of the description provides a method for establishing a session to provide content to a plurality of User Equipment (UE) using at least one multicast and broadcast data transmission. Such a method includes receiving, through a Session Management Function (SMF) from a central network (CN), a request for an authenticated UE accessing content targeted to the plurality of UEs. The method also includes requesting, through the CN SMF, authorization of a CN unified data management function (UDM) that is configured to receive information from members of a member function. This method also includes initiating, by the SMF of the CN, the transmission of a decoding code towards the UE. In some embodiments, the member function is at least one of: instantiated as a central network function with member information stored within the central network, but provided by the content provider; and located external to the central network. In some embodiments, member information is received via another central network function. In some modalities, the method still includes, after receiving the request, forwarding, through the SMF of CN, the request
Petition 870190077600, of 8/12/2019, p. 25/69
6/41 to a central server (CN) authentication server (AUSF) function to authenticate the UE. In some modalities, initiating, by the CN SMF, the transmission of a decoding code towards the UE includes at least one among: transmitting, by the CN SMF, a decoding code previously stored towards the UE; and request, by the SMF of the CN, the decryption code of a function of the authentication server (AUSF) of a central network (CN).
[0014] Another aspect of the description provides a method for delivering content from a content provider to a plurality of UEs, the method performed by a flat user function (UPF) from a central network (CN). This method includes receiving, by the UPF of the CN, content provided by the content provider to the plurality of UEs, storing, by the UPF of the CN, the content in a cache function; receive an encryption code from an authentication server role (AUSF). Such a method also includes receiving the contents of a cache function. Such a method also includes encoding the received content using the encoding code to produce encoded content; and transmitting the encoded content towards the plurality of UEs through at least one Radio Access Network (RAN) node. In some embodiments, transmission of the encoded content includes multicasting the encoded content to each of at least one RAN node. In some embodiments, the transmission of the encrypted content includes transmitting the encrypted content to each of at least one RAN node. In some embodiments, the cache function is a central network cache function. In some modalities, the UPF is configured to support multicast and broadcast data distribution to multiple (R) AN nodes and receiving the content from a cache function includes receiving the content over an interface. In some embodiments, transmitting the encoded content towards the plurality of UEs includes transmitting the encoded content using an interface.
Petition 870190077600, of 8/12/2019, p. 26/69
7/41 [0015] Another aspect of the description provides a central network (CN) authentication server (AUSF) function to deliver content from a content provider to a plurality of User Equipment (UE) using at least one transmission multicast and broadcast data, AUSF configured to implement any of the steps of the methods described here. For example, this aspect provides a central server (CN) authentication server (AUSF) function to deliver content from a content provider to a plurality of User Equipment (UE) using at least one multicast and broadcast data transmission , AUSF including a network interface; a processor; and non-transitory machine-readable media. Machine-readable media stores machine-executable instructions that, when executed by the processor, cause the AUSF to: receive a request for an authenticated UE to access content targeting the plurality of UEs; receive security information comprising a decryption code from a security function that provides the decryption code for use by the authenticated UE to decode the content; and send the decryption code towards the authenticated UE.
[0016] It should be noted that in some modalities the machine-readable media still stores instructions for implementing the method steps disclosed here.
[0017] Another aspect of the description provides a flat user function (UPF) of a central network (CN) to deliver content from a content provider to a plurality of User Equipment (UE) using at least one multicast data transmission and broadcast, the UPF configured to implement any of the method steps described here. For example, this aspect provides a flat user function (UPF) from a central network (CN) to deliver content from a content provider to a plurality of User Equipment
Petition 870190077600, of 8/12/2019, p. 27/69
8/41 (UE) using at least one multicast and broadcast data transmission, the UPF including a network interface; a processor; and non-transitory machine-readable media. Machine-readable media stores machine-executable instructions that, when executed by the processor, cause UPF to: store the content provided from the content provider in a cache function; receive an encryption code from a central network authentication server (AUSF) function; receive the contents of the cache function; encode received content using the encoding code to produce encoded content; and transmit the encoded content towards the plurality of UEs through at least one Radio Access Network (RAN) node.
[0018] It should be noted that in some modalities the machine-readable media still stores instructions for implementing the method steps disclosed here.
[0019] Another aspect of the description provides a Session Management Function (SMF) from a central network (CN) to establish a session to deliver content from a content provider to a plurality of User Equipment (UE) using at least one multicast and broadcast data transmission, SMF configured to implement any of the steps of the methods described here. For example, such an aspect provides a Session Management Function (SMF) from a central network (CN) to establish a session to deliver content from a content provider to a plurality of User Equipment (UE) using at least one broadcast. multicast and broadcast data, SMF including a network interface; a processor; and non-transitory machine-readable media. Machine-readable media stores machine-executable instructions that when executed by the processor make SMF: receive
Petition 870190077600, of 8/12/2019, p. 28/69
9/41 a request for an authenticated UE to access content targeting the plurality of UEs; request authorization from a CN unified data management function (UDM) that is configured to receive information from members of a member function; and start, by the CN SMF, the transmission of a decoding code towards the UE.
[0020] It should be noted that in some modalities the machine-readable media still stores instructions for implementing the method steps disclosed here.
BRIEF DESCRIPTION OF THE FIGURES [0021] Other features and advantages of the present invention will become apparent from the following detailed description, taken in combination with the accompanying drawings, in which:
[0022] Figure 1 illustrates, in a component diagram, an example of a communication network architecture;
[0023] Figure 2 illustrates, in a component diagram, an example of an architecture of the multicast and broadcast multimedia subsystem (MBMS) for the evolved package system (EPS);
[0024] Figure 3 illustrates, in a component diagram, an example of a reference architecture for the evolved package system with evolved universal terrestrial radio access network (E-UTRAN) and UTRAN in the MBMS broadcast mode;
[0025] Figure 4 illustrates, in a component diagram, an example of a network architecture having MBMS capabilities, according to an embodiment of the present description;
[0026] Figure 5 illustrates, in a component diagram, a second example of a network architecture having MBMS capabilities, according to an embodiment of the present description;
[0027] Figure 6 illustrates, in a component diagram, a third example of a network architecture having MBMS capabilities, of
Petition 870190077600, of 8/12/2019, p. 29/69
10/41 according to one embodiment of the present description;
[0028] Figure 7 illustrates, in a component diagram, a fourth example of a network architecture having MBMS capabilities, according to an embodiment of the present description;
[0029] Figure 8 illustrates, in a component diagram, a fifth example of a network architecture having MBMS capabilities, according to an embodiment of the present description;
[0030] Figure 9 illustrates, in a flowchart, an example of a method to provide access to an MBMS transmission, according to examples of the network architecture;
[0031] Figure 10 illustrates, in a flowchart, an example of a method of transmitting a secure transmission of MBMS, according to examples from the network architecture.
[0032] Figure 11 illustrates, in a block diagram, an example of a server located in the subnet that implements a network function; and [0033] Figure 12 illustrates, in a block diagram, a computer system that can be used to implement the devices and methods disclosed here.
[0034] Figure 13 is a call flow diagram illustrating a method according to a modality.
[0035] It will be noted that throughout all the attached drawings, similar features are identified by similar reference numerals. DETAILED DESCRIPTION [0036] Modalities of the present invention are directed to network architectures having multicast and broadcast multimedia subsystem (MBMS) capabilities.
[0037] Figure 1 illustrates, in a component diagram, an example of a communication network architecture 100. Communication network architecture 100 comprises user equipment
Petition 870190077600, of 8/12/2019, p. 30/69
11/41 (UE) 110, an access network (AN) 120, a central network (CN) 130 and a data network (DN) 140. AN 120 can be a radio access network (RAN). The term “(R) AN” in this description denotes that an AN can be an RAN. The UE 110 communicates with a DN 140 ka via the (R) AN 120 and CN 130. The message packet data units (PDUs) sent between the UE 110 and the DN 140 pass through the (R) AN 120 and of CN 130. A DN 140 can be a public network operator, a private data network such as a local area data network (LADN), an intraoperator data network, or any other type of data network.
[0038] In an uplink direction (UL), the PDUs of the user plane (UP) and the control plane (CP) pass from UE 110 to (R) AN 120 through a communication link. The (R) AN 120 then forwards the UP and CP PDUs to CN 130 which then forwards the UP PDUs to DN 140. In a downlink direction (DL), the UP PDUs pass from DN 140 to CN 130. A CN 130 then forwards the UP PDUs, and can send the CP PDUs to (R) AN 120 which then forwards the UP and CP PDUs to the UE 110. The CP functionality on the CN 130 configures the UP functions on the CN 130 to provide traffic management functionality for a session. One or more UP functions per session can be activated and configured by the CP functionality for a given UP scenario.
[0039] The connections between the components of the communication network architecture 100 can be suitable for any communication channel. For next generation (NG) architectures, such as fifth generation mobile wireless networks (5G), the connection between the UE 110 and an (R) AN 120 can be a wireless connection. The connection between the (R) AN 120 and the CP of the CN 130 can be via an NG2 interface. The connection between the (R) AN 120 and the UP of the CN 130 can be via an NG3 interface. The connection between the UP of CN 130 and DN 140 can be
Petition 870190077600, of 8/12/2019, p. 31/69
12/41 through an NG6 interface, [0040] Figure 2 illustrates, in a component diagram, an example of an architecture of the multicast and broadcast multimedia subsystem (MBMS) 200 for an evolved package system (EPS). The MBMS 200 architecture comprises at least one UE 110 (in this example, MBMS 210 receivers), at least one (R) AN 120 (in this example, a universal terrestrial radio access network (UTRAN) 222 and an evolved UTRAN ( E-UTRAN) 224 are implemented on separate RANs 120), a CN 130, at least one DN 140 (in this example, an internet protocol network (IP) 242 is implemented as DN 140), and a content provider 150 It is observed that sometimes the term UTRAN is defined as “terrestrial radio access network (UMTS) for univeral mobile telecommunications service”. Regardless of the full name used for UTRAN, both names refer to the same UTRAN.
[0041] MBMS 210 receivers can receive wireless signals from (R) AN 120 (UTRAN 222 or E-UTRAN 224) to which they are connected. RANs 120 are also connected to CN 130 through a backbone connection. CN 130 includes an MBMS gateway (MBMS GW) 235. DN 140 (IP network 242) includes a broadcast-multicast service center (BM-SC) 245. BM-SC 245 can be a mobile margin application (MEC). CN 130 is connected to DN 140 via the SGmb and SGi ~ mb interfaces between the MBMS GW 135 and the BM-SC 245. A content provider 150 can be connected to the BM-SC 245 via an xMB interface.
[0042] Figure 3 illustrates, in a component diagram, an example of a reference architecture 300 for a package system evolved with E-UTRAN and UTRAN in the MBMS broadcast mode. Reference architecture 300 includes at least one user equipment (UE) 110, at least one (R) AN (in this example, a UTRAN 222
Petition 870190077600, of 8/12/2019, p. 32/69
13/41 and an E-UTRAN 224), a mobility management entity (MME) 332 of a CN 130, a general service packet radio service (GPRS) supporting node (SGSN) 334 of a CN 130, an MBMS GW 235 from a CN 130, a gateway from DN 342 to a DN 140, the BM-SC 245 from a DN 140, and the content provider 150. UEs 110 can communicate wirelessly with (R ) ANs 120 through a Uu interface for LJTRAN 222 and through a Uu interface E-UTRAN for E-UTRAN 224. UTRAN 222 can communicate with MBMS GW 235 through an M1 interface to send and receive data packets, and with SGSN 334 through a lu interface to send and receive control packets. The SGSN 334 can communicate with the MBMS GW 235 through an Sn interface to send and receive control packets. The E-UTRAN 224 can communicate with the MME 332 through an M3 interface to send and receive control packets, and with the MBMS GW 235 through an M1 interface to send and receive data packets. The MME 332 can communicate with the MBMS GW 235 through an Sm interface to send and receive control packets. The BM-SC 245 supports separate unicast transmissions or sessions (via an SGi interface) and multicast / broadcast transmissions or sessions (via an SGi-mb interface). The BM-SC 245 comprises a MBMS 346 bearer service for distributing BM-SC 245 data to UEs 110, and an MBMS 348 user service to manage the UE subscription, and security and billing information. MBMS GW 235 can communicate with the MBMS 348 carrier service through the SGmb interface for unicast transmissions and through the SGi-mb interface for multicast / broadcast transmissions. The DN 342 gateway can communicate with the MBMS 348 carrier service through the SGi interface. The content provider 150 can communicate with the BM-SC via an appropriate data connection. It should be noted that PDN 342 can establish unicast carriers
Petition 870190077600, of 8/12/2019, p. 33/69
14/41 to send data from BM-SC 245 to multiple UEs 110.
[0043] It is observed that Figure 3 illustrates a 4G network in which the components, for example, MME 332, MBMS GW 235, BM-SC 245, etc., represent dedicated hardware components (for example, network elements) of network. 5G networks are expected to provide more flexible architectures, allowing multiple network functions to reside in hardware components flexibly configured using network function virtualization (NFV). It is also anticipated that 5G networks will provide flexible virtual networks (VNs) and the allocation of resources to services or VNs through the division of the network. Therefore, the modalities discussed here propose systems, architectures and methods to provide MBMS capabilities in 5G networks.
[0044] Several examples of network architectures with MBMS capabilities will now be described with reference to Figures 4 to 8. It should be noted that some components in each figure and example may be the same component (and are shown in the figures with the same number of reference). Wherever a description of any of these same components and their functions is not repeated in one example, then it should be understood that a description in another example for that same component applies.
[0045] Figure 4 illustrates, in a component diagram, an example of network architecture 400 having MBMS capabilities, according to an embodiment of the present description. The network architecture 400 can be a fifth generation (5G) network architecture and comprises a subarchitecture (R) AN 420, a subarchitecture CN 430 and a subarchitecture BM-SC 440.
[0046] The (R) AN 420 subarchitecture comprises at least one UE 110, at least one (R) AN 120 and an MBMS RAN management function (MRMF) 425. A UE 110 can communicate with one (R) AN 120 through a suitable wired connection or connection without
Petition 870190077600, of 8/12/2019, p. 34/69
15/41 thread. The MRMF 425 can communicate with an (R) AN 120 through an NG MRMF-ΑΝ interface. The MRMF 425 can manage at least one of the multicast and broadcast data transmissions to multiple 120 RANs. Note that unicast data transmission can be a special case of multicast data transmission, where only one UE 110 joins the multicast data transmission; some multicast session data transmission parameters can be modified to serve a single UE 110 or simply an existing unicast radio carrier is used for unicast data transmission.
[0047] The CN 430 subarchitecture comprises a flat user function (UPF) 431 which comprises the MBMS GW 235 or supports equivalent features of MBMS GW 235, a function of the authentication server (AUSF) 432, a data management function unified (UDM) 433, a network exposure function (NEF) 434, an access and mobility management function (AMF) 435, a session management function (SMF) 436 and a policy control function (PCF) 437. AUSF 432 provides security functions, such as user authentication and user requests, and security keys used for the encryption and decryption of data transmitted by interfaces, such as interfaces between the UE 110 and the UPF 431. The UDM
433 provides storage management for the network and user information, and security measures to protect the data. NEF
434 provides connections for MBMS control functions and CN control plan (CPF) functions through an MBMSNEF NG interface. The AMF 435 manages the termination of the signaling Interfaces NG1 and NG2, manages the routing of signaling messages from an UE 110 and an (R) AN 120 to SMF 436, and manages mobility and security procedures for UEs 110. The SMF 436 manages the establishment of a UP connection between an UE 110 and a DN 140. The
Petition 870190077600, of 8/12/2019, p. 35/69
16/41
PCF 437 provides policies for different network functions to manage an UE session. Such policies include quality of service (QoS), mobility management, session management and billing policies. Table 1 shows the interfaces that connect some of the components of the CN 330 subarchitecture with other components of the CN 330 subarchitecture.
Component Interface Component AUSF 432 NG13 UDM 433 AUSF 432 NG12 AMF 435 AUSF 432 NG AUSF-NEF NEF 434 UDM 433 NG UDM-NEF NEF 434 UDM 433 NG8 AMF 435 UDM 433 NG10 SMF 436 NEF 434 NG PCF-NEF PCF 437 AMF 435 NG14 AMF 435 AMF 435 NG11 SMF 436 AMF 435 NG15 PCF 437 SMF 436 NG7 PCF 437 SMF 436 NG4 UPF (MBMS GW) 431 UPF (MBMB GW) 431 NG9 UPF (MBMS GW) 431
Table 1: Communication Interfaces between CN Components [0048] Although the above point-to-point interfaces connecting two network functions are described, service-based interfaces (SBI) can also be used, for example, as described in the 3GPP TS Technical Standard 23.502, entitled “Procedures for the 5G System”. For example, in a service-based view, AMF 435 can communicate with other functions of the central network's control plan through a service-based interface denoted as Namf (not shown). The SMF 436 can communicate with other major network functions, in a service-based view, through
Petition 870190077600, of 8/12/2019, p. 36/69
17/41 a service-based interface denoted as Nsmf. The SMF 436 can also connect to an UPF 212 through a logical interface, such as the NG4 network interface. As another example, the Authentication Server Role (AUSF) 432, provides authentication services for other network functions through a service-based Nausf interface.
[0049] In the subarchitecture of (R) AN 420, the MRMF 425 can perform the selection of a suitable radio carrier on the 5G radio access node (gNB) (for example, selecting a unicast, a multipoint point of a single cell (SC-PTM) or a broadcast radio channel). The MRMF 425 can also coordinate the broadcast resources of multiple radio nodes for the same MBMS service. An NG MRMFAMF interface connects MRMF 425 and CN 130. In particular, MRMF 425 can communicate with AMF 424 via the NG MRMFAMF interface. The SMF 436 can send to the MRMF 425, through the AMF 424, information pertaining to the UE 110 that are accessing the MBMS services. The UE 110 can communicate with the AMF 424 through an NG1 interface.
[0050] A (R) AN 120 mode can communicate unicast CP packets with AMF 324 through an NG2 interface. An NG MRMF-ΑΝ interface transmits MBMS control information between the MRMF 425 and the (R) AN 120 nodes. The MRMF 425 can send the radio channel type for DL MBMS ( for example, unicast, SC-PTM or broadcast radio channel) and allocation of broadcast resources (for example, carrier frequency, resource block number, etc.). (R) AN 120 nodes can send MRMF 425 radio resource availability, including which resources are in use, for MRMF to select the radio carrier. (R) AN 120 nodes receive unicast DL data (at least one of the UP packets and sessions) from the UPF 431 through an NG3 interface
Petition 870190077600, of 8/12/2019, p. 37/69
18/41 and receive DL MBMS multicast data (at least one of the packets and DL sessions transferred from MBMS) The GW 235 implemented in UPF 431 through an NG3-MBMS interface. It is noted that while in this example the MBMS GW 235 is implemented in the UPF 431, the MBW GW function alone can be a type of UPF 431. Furthermore, an MBMS GW can be colocalized with an UPF 431 or an integral part of the UPF 431. It should be noted that in some modalities, the MG MSGW in Figures 4-8 can be integrated into the UPF 431 by adding software features that run features of the MBMS GW 235.
[0051] The subarchitecture of BM-SC 440 can be implemented in a node of DN 140 and comprises a member function (MF) 441, a security function (SF) 442, a transport and proxy function (PTF) 443, a session and transmission function (STF) 444, a service announcement function (SAF) 445 and a cache function (CF) 446. An NG5 interface can communicate QoS information and other information between MF 441 and PCF 437 MF 441 can still communicate with PTF 443. SF 442 can communicate with STF 444. PTF 443 can still communicate with STF 444. STF 444 can still communicate with SAF 445 and with CF 446. CF 446 can comprise cache for content received from at least one from content provider 150 and cache for content that has been sent for transmission. SF generates security codes for a point-to-point connection, from the application server in the DN to the UPF, and from the UPF to the UE.
[0052] As noted above, NEF 434 provides connections for MBMS control functions and CN CPF via the NG NEFMBMS interface. MBMS SF 442 performs security procedures with CN AUSF 432. When a UE 110 performs a network connection procedure, the UE 110 and AUSF 432 also perform bilateral authentication. After successful authentication, AUSF 432 sends to the UE
Petition 870190077600, of 8/12/2019, p. 38/69
19/41
110 security keys for data encryption in the uplink and data decryption in the downlink. During or after completing the network connection procedure, the UE 110 can request an MBMS service. The AUSF 432 acts as a midpoint for transferring security messages between the UE 110 and the MBMS 442 security function. The MBMS SF 442 sends the security code to the UE 110 to encrypt or decrypt the data on the UP. MBMS SF 442 can provide authentication service to verify the identity of the UE. [0053] It is understood that the NG1 interface is used to transfer CP information between the EU 110 and CN 430 CP functions. Therefore, a person skilled in the art can understand that a way to provide security from AUSF 432 to the UE 110 is either via AMF 435, or via SMF 436 and AMF 435.
[0054] The membership function MBMS 441 manages, communicates and sends membership data to UE 110 (for example, subscription data, QoS policy and MBMS content access server locations) through an NG MBMS-NEF interface a NEF 434 UE 110. NEF 434 sends UDM 433 subscription data (that is, to ensure that UE 110 has a subscription) received from MBMS MF 441. NEF 434 sends to PCF 437 QoS policy and locations of MBMS server for accessing content received from MBMS MF 441. Alternatively, when the UE 110 sends a request for an MBMS service to the SMF 436, the SMF 436 can contact the MF 441 of the BM-SC 440 to obtain service authorization. In some embodiments, the SMF 436 can communicate with the MF 441 using an SBI. Alternatively, the SMF 436 can communicate with the MF 441 via a user plane interface (UP). For example, SMF 426 can send the authorization request message to the same or different UPF 431, which may or may not have MBMS GW functionality. This UPF 431 forwards
Petition 870190077600, of 8/12/2019, p. 39/69
20/41 the authorization request message to MF 441 directly or indirectly through another function of BM-SC 440, such as RTF 443.
[0055] In some modalities, interfaces, such as NG MBMSNEF, can be implemented using an SBI interface. This can allow for direct communication between a function of the CN 430 and a function of the BM-SC 440. For example, the SF 442 of the BM-SC 440 can provide a service that provides encryption and decryption keys for content protection. Consumer functions, such as AUSF 432 or SMF 436, can obtain the SF 442 encryption and decryption keys using the SF 442 service. Similarly, the MF 441 can provide a UE Subscription Service. Consumer functions, such as UDM 433 or SMF 436, or PCF 437, can obtain the EU subscription for MBMS services using the MF441 EU Subscription Service.
[0056] In some modalities, PTF 443 can be configured to use the SBI provided by the CN 430 functions. For example, PTF 443 can send a request to CN 430 to establish UP connections. The PTF 443 order can be sent to PCF 437, or NEF 434 using PCF 437 SBI or NEF 434, respectively. PTF 443 can send MBMS session information, which can include MBMS session location information (for example geographic zone identifiers), time information (start time, end time or length / duration of the MBMS session ), UE information, such as External Identifiers, UE group information (such as External Group Identifier), UE Categories, Device Class), QoS information (such as Maximum Bit Rate, Resource Type (e.g. GBR, non GBR, GBR critical delay) Maximum Bit Flow, Guaranteed Flow Bit Rate, Packet Delay Budget, Packet Error Rate), application layer protocol information (e.g. Dynamic HTTP Adaptation (DASH) ) what
Petition 870190077600, of 8/12/2019, p. 40/69
21/41 can be used by the CN functions to optimize the operation and / or be sent to the UEs 110.
[0057] In some modalities, messages between a CN 430 function and a BM-SC 440 function can be exchanged through NEF 434 using the SBI interface. This would help to provide CN protection
430 electronic counterattacks.
[0058] MBMS PTF 443 and SAF 445 are connected with UPF
431 (MBMS GW 235) through NG6 interfaces for unicast content data and through NG6-MBMS interfaces for broadcast content and control information for UPF content processing. For example, the UPF 431 can perform the function of an adaptive dynamic flow client over Hypertext Transfer Protocol (HTTP) (DASH) to retrieve video segments from the DASH server of a 150 content provider. The NG6-MBMS interface allows a single encryption code to be used with CN 130 for all multicasts and broadcasts, which include unicast as a special case.
[0059] Figure 5 illustrates, in a component diagram, a second example of a network architecture 500 having MBMS capabilities, according to an embodiment of the present description. The network architecture 500 can be a 5G network architecture and comprises the subarchitecture (R) AN 420, a subarchitecture of CN 530 and a subarchitecture of BM-SC 540. This second example of a network architecture 500 integrates some control functions MBMS at CN CPF, thus simplifying the architecture of the BM-SC 540, which can reduce the cost of an MBMS system. In addition, the delay in configuring the service and the number of signaling messages are reduced. In this 500 architecture, the MBMS data processing functions remain outside the CN in the BM-SC 540 of the DN 140. The subarchitecture (R) AN 420 remains as described in Figure 4.
[0060] The security function of MBMS (SF) 542 is integrated with
Petition 870190077600, of 8/12/2019, p. 41/69
22/41 to AUSF 532. A first part of the member function (MF) 541a that manages subscription data (including which services the UE 110 has a subscription to) is merged with UDM 533. A second part of the subscription function member (MF) 541b that manages the QoS policy, and the MBMS server locations for content access is joined with PCF 537.
[0061] PTF 443 of MBMS and SAF 445 are connected with UPF (MBMS-GW) 431 through NG6 interfaces for unicast data, and via NG6-MBMS interfaces for multicast or broadcast data. The content data provided from the PTF 443 of the BM-SC 540 to the UPF 431 can be encoded in the BM-SC 540. The UPF 431 can then decode the content data to perform processing on the network, such as transcode video. Thus, a single encryption scheme for each UPF 431 can be used to encrypt data transmitted between the BM-SC 540 and the UPF 431. The UPF 431 can also request user information, such as encryption keys, from the CN CPFs to encrypt the content data again for secure transmission over the air interface. Program information provided from SAF 445 from BM-SC 540 to UPF 431 can also be treated in the same manner as described above for content data. Note that there are two ways to send program information to the UE 110. One way is broadcast (or multicast) via the NG6-MBMS interface. The other mode is a unicast transmission through the NG6 interface, where the UE 110 can access the SAF server to download the program information. It is noted that, in some modalities, the UPF 431 can use another interface to transmit data to the UE 110 through (R) AN 12. For example, if the UPF 431 received broadcast (or multicast) data through the NG6 interface -MBMS, can transmit broadcast (or multicast) data through the NG3-MBMS interface and, similarly, use the NG3 interface to
Petition 870190077600, of 8/12/2019, p. 42/69
23/41 unicast data received via NG6 interface. However, some modalities may change the interface if circumstances warrant. For example, if multiple UPFs are instantiated to serve individual UEs, then the UPFs can receive broadcast (or multicast) data via the NG6-MBMS interface directed to each of a plurality of UEs, but each UPF can be configured for unicast transmissions. for the particular EU that this UPF serves.
[0062] Figure 6 illustrates, in a component diagram, a third example of a network architecture 600 having MBMS capabilities, according to an embodiment of the present description. The network architecture 600 can be a 5G network architecture and comprises the subarchitecture (R) AN 420, a subarchitecture of CN 630 and a subarchitecture of BM-SC 640. The network architecture 600 integrates the security function MBMS (SF) 542 to CN AUSF 532, thus simplifying the BM-SC 640 architecture, which can reduce the cost of an MBMS system. In addition, the delay in configuring the service and the number of safety signal messages are reduced. In this 600 architecture, the MBMS (MF) member function 441 remains on the BM-SC 640, allowing independent association management on the BMSC 640 from DN 140. The MBMS data processing functions also remain outside the CN on the BM-SC 640 from DN 140. The subarchitecture of (R) AN 420 remains as described in Figure 4 [0063] The 443 proxy and transport (PTF) MBMS function and the 445 service announcement function are connected to the 431 via UPF (MBMS- GW) via NG6 interfaces for unicast data and via NG6-MBMS interfaces for multicast or broadcast data. Content data provided by PTF 443 from BM-SC 640 to UPF 431 can be encoded in BM-SC640, for example by PTF 443. Then, UPF 431 can decrypt content data to perform processing on the network, such as transcoding of video. Thus, a single
Petition 870190077600, of 8/12/2019, p. 43/69
24/41 encryption for each UPF 431 can be used to encrypt data transmitted between the BM-SC 640 and the UPF 431. The UPF 431 can also request user information, such as encryption keys, from CN CPFs to encrypt data from content again for secure transmission over the air interface. Program information provided from SAF 445 from BM-SC 640 to UPF 431 can also be treated in the same manner as described above for content data. Note that there are two ways to send program information to the UE 110. One way is broadcast (or multicast) via the NG6-MBMS interface. The other mode is a unicast transmission through the NG6 interface, where the UE 110 can access the SAF server to download the program information. Data transmission to the UE 110 via (R) AN 12 which was received at the UPF from the BM-SC 40 is similar to the description above.
[0064] Figure 7 illustrates, in a component diagram, the fourth example of network architecture 700 having MBMS capabilities, according to one embodiment of the present description. The network architecture 700 can be a 5G network architecture and comprises the subarchitecture (R) AN 420, a subarchitecture of CN 730 and a subarchitecture of BM-SC (AF) 740. The network architecture 700 integrates a first part of the function MBMS (MF) member 541a, which manages subscription data (including services to which UE 110 has a subscription), with UDM 533 and integrates a second part of MBMS membership. Function (MF) 541 b, which manages QoS policy and MBMS server locations for accessing content, with PCF 534. Thus, the architecture of the BM-SC 740 is simplified, which can reduce the cost of a MBMS system. In addition, the session establishment procedure can be simplified, as CN 130 does not need to verify the user's signature with the BM-SC 740 and, therefore, the number of member signature signaling messages is reduced.
Petition 870190077600, of 8/12/2019, p. 44/69
25/41
In this 700 architecture, MBMS (SF) 442 security remains on BMSC 740, allowing independent third party security measures to protect content on the BM-SC 740 from DN 140. The MBMS data processing functions remain outside the CN on the BM- SC 740 from DN 140. The subarchitecture of (R) AN 420 remains as described in Figure 4.
[0065] The 443 proxy and transport function (PTF) MBMS and the 445 service announcement function are connected with the UPF (MBMS-GW) 431 via UPF (MBMS-GW) via NG6 interfaces for unicast data and via NG6 interfaces -MBMS for multicast or broadcast data. The content data provided from the PTF 443 of the BM-SC 740 to the UPF 431 can be encoded in the BM-SC 740. Then, the UPF 431 can decode the content data to perform processing on the network, such as video transcoding . Thus, a single encryption scheme for each UPF 431 can be used to encrypt data transmitted between the BM-SC 740 and the UPF 431. The UPF 431 can also request user information, such as encryption keys, from the CN CPFs to encrypt content data again for secure transmission over the air interface. Program information provided from SAF 445 from BM-SC 740 to UPF 431 can also be treated in the same manner as described above for content data. Note that there are two ways to send program information to the UE 110. One way is broadcast (or multicast) via the NG6-MBMS interface. The other mode is a unicast transmission through the NG6 interface, where the UE 110 can access the SAF server to download the program information. Data transmission to the UE 110 via (R) AN 12 which was received at the UPF from the BM-SC 40 is similar to the description above.
[0066] Figure 8 illustrates, in a component diagram, a fifth example of an 800 network architecture having
Petition 870190077600, of 8/12/2019, p. 45/69
26/41
MBMS, according to an embodiment of the present description. The 800 network architecture can be a 5G network architecture and comprises the (R) AN 420 subarchitecture and a CN 830 subarchitecture. The 800 network architecture integrates the control functions of the BM-SC with the CPF of the CN, and the data processing functions of the BM-SC with the UPF 831, thus simplifying the architecture of the BM-SC, which can reduce the cost of an MBMS system. In addition, the delay in configuring the service and the number of signaling messages are reduced. The subarchitecture of (R) AN 420 remains as described in Figure 4 [0067] MBMS SF 542 is integrated with AUSF 532. A first part of the membership function (MF) 541a that manages subscription data (including services to members) which UE 110 has a subscription to) is joined to UDM 533. A second part of the membership function (MF) 541b that manages the QoS policy and MBMS server locations for accessing content is merged with PCF 537.
[0068] The MBMS proxy and transport function is integrated with UPF (MBMS GW) 831, allowing localized MBMS services (for example, for vehicle communications where traffic updates are located). UPF (MBMS GW) 831 comprises four UP functions similar to those of a BM-SC: an MBMS distribution entity 843, an STF 444, SAF 445 and CF 446. The MBMS distribution entity 843 performs multicast transmission with multiple (R) AN 120 nodes through the NG3-MBMS interface. SMF 436 controls the configuration of the multicast session between the UPF (MBMS GW) 831 and the (R) AN 120 nodes through the NG4 and NG2 interfaces, respectively. An NG6-MBMS interface between the UPF (MBMS GW) 831 and a content provider 150 can carry content and in-band control messages.
[0069] Since the functions of the BM-SC subsystem are integrated
Petition 870190077600, of 8/12/2019, p. 46/69
27/41 graded on the CN 830, some features of the BM-SC can be performed by some functions of the CN 830, as explained above. Another example of functionality integration is that the PTF 443 of the BM-SC subsystem is implemented in the MBMS Distribution function 843. The MBMS 843 Distribution function is a part of UPF 831; and can generate billing records for Content Provider 150. The MBMS Distribution function can send billing records to PCF 537 via SMF 436; PCF 537 can send billing records to Content Provider 150 directly or via NEF 434. Alternatively, MBMS Distribution 843 can send billing records to Content Provider 150 directly using a separate interface. Alternatively, the MBMS 843 Distribution may send collection records to the Content Provider 150 via STF 444.
[0070] From this description, one skilled in the art would understand that the transmission of multicast or broadcast data can be established by CP functions. For example, SMF can establish UP connections between UPF 431 and (R) AN 120. AMF 435 responsible for managing access and mobility for UE 110. UE 110 can request an MBMS service, which can be handled by CN's CP Functions. For example, SMF 436 would associate the UE with an MBMS session. The AUSF 432 can provide encryption and / or decryption keys to the UE 110 via SMF 436 during the MBMS session connection.
[0071] In summary, in Figure 5, the functionality of the functionality of the MF and SF functions is moved from BM-SC to CN. In Figures 6 and 7, only the MF and SF functions are moved from BM-SC to CN. In Figure 8, the functionality of the entire BM-SC is moved to the CN, eliminating the need for a separate BM-SC node. There are advantages to
Petition 870190077600, of 8/12/2019, p. 47/69
28/41 move these functions to the CN. In figure 8, the cost of dedicated hardware for BM-SC is eliminated completely, while in Figures 57 the cost of BM-SC is reduced. This can help to optimize capacity, as BM-SCs tend to be fixed costs that can be underutilized for some periods of time and overloaded for others. However, by reusing the general purpose NC infrastructure, resources can be allocated to MBMS services as needed. In addition, moving the functions of the BMSC subsystem to the CN can reduce the overhead used by the CP signaling between the BM-SC and the CN. In addition, for the modality illustrated in Figure 8, the overhead associated with the UP interfaces NG6 and NG6-MBMS is also eliminated. In addition, multicast-broadcast can be deployed more quickly, for example, by installing additional software that runs the BM-SC functionalities in the same CN functions as the data center.
[0072] Figure 9 illustrates, in a flowchart, an example of a 900 method to provide access to an MBMS transmission, according to examples from the 400 network architecture. The 900 method can be performed by an AUSF 432 from a CN 130. During or after the completion of a network connection procedure, a UE 110 may request an MBMS service. The MBMS 442 security function sends a security code to access the MBMS service to NEF, via the NG MBMS-NEF interface (for AUSF). The AUSF 432 then receives the security code (910) from NEF 434 via the NG AUSF-NEF interface. AUSF 432 then sends the security code to UE 110 (920) via AMF 435. UE 110 now has access to the transmission of the MBMS. Consequently, it should be appreciated that in step 920, AUSF sends the security code to the UE, through intermediate nodes, which in this example includes AMF 435. From the network architecture in Figure 4, one skilled in the art can understand that AMF
Petition 870190077600, of 8/12/2019, p. 48/69
29/41
435 forwards the security code to UE 110 through the NG1 interface, it being understood that the NG1 interface crosses the (R) AN 120. [0073] Figure 10 illustrates, in a flowchart, an example of a method 1000 of transmitting the secure transmission of MBMS, according to examples from the 500,600,800 network architecture. Method 1000 can be performed by an AUSF 532 of a CN 130, and the ALJSF 532 comprises sending an UPF 431,831 a first security code to decode an MBMS transmission requested by UE received in UPF 431,831 by an NG6-MBMS interface. The AUSF 532 then sends the UPF 431,831 a second security code to encode the MBMS transmission to be sent to a (R) AN via an N3MBMS interface so that the (R) AN can forward the transmission to the UE request. .
[0074] The NG4 interface is used for SMF 436 to send the CP information to UPF 431. Thus, one skilled in the art can understand that security codes for encoding and decoding MBMS data can be sent from AUSF 532 to SMF 436 , in this case SMF
436 forwards security codes to UPF 431, through AMF 435.
[0075] In some modalities SMF 436 receives information from members of the unified data management function (UDM) 433 in order to authorize the request for a UE 110. In some modalities, UDM 433 receives information from members of MF 441 In some modalities, this is received from an external interface, for example, when the MF 441 is located inside the BM-SC. In some modalities, UDM 433 received information from members of MF 441 through internal signaling, for example, when MF 441 is integrated within UDM 433.
[0076] Figure 13 is a call flow diagram illustrating a method according to a modality. Step 701a illustrates an order
Petition 870190077600, of 8/12/2019, p. 49/69
30/41 MB session establishment being sent from one of the UEs 110 to SMF 436, via (R) AN 120 and AMF 435. Note that the MB session may exist and a UE 110 may join this session Existing MB through this order. The UE 110 may include in the MB session request information to identify the UE (for example, SUPI and / or GPSI), information to identify the service request (such as MB service), content information to identify the required content (e.g. TV channel, movie name and the like) and the Session ID MB, if the UE knows the Session ID MB. SMF 436 can optionally send a request to AUSF 432 in step 701b for an authentication procedure between CN and UE 110. SMF 436 can include information for AUSF 432 to identify the service that the UE requests, for example, a TV channel identifier, a content identifier (such as a movie name), an MB Session Identifier, an EU identifier (for example, SUPI (Subscription Permanent Identifier), 5G GPSI (Generic Public Signature Identifier)) , UE Group Identifier. It should be noted that AUSF can receive the request via an intermediate network function. In any case, the AUSF receives a request for a UE from the plurality of UEs 110 to access content directed to the plurality of UE 110. An optional authentication process (703) takes place between the UE and AUSF 432. Some UEs 110 they may be designed for the MBMS service only and therefore may not be necessary to register with the CN. This type of device may be required to perform the 703 authentication procedure to receive the MBMS service. The 703 authentication procedure is indicated as optional for the UE which may have been previously authenticated as part of a network attachment. In some embodiments, the 703 authentication procedure may involve AMF 435, since AMF 435 can serve as a security anchor point.
Petition 870190077600, of 8/12/2019, p. 50/69
31/41
In this case, AUSF 432 can send security information to AMF 435, and AMF 435 performs an authentication procedure with UE 110 for the MBMS service. After completing the 703 authentication procedure, AUSF 435 sends a response in step 701c to SMF 436.
[0077] An alternative implementation of step 701b that SMF 436 can send a request to AMF 435 to authenticate the UE 110. The request includes the UE ID (such as SUPI), MB Session Identifier, information to identify the UE Service Request. AMF 435 performs authentication procedure 703, which can involve AUSF 432, obtaining a security code for secure communication through the radio interface. In authentication procedure 703, the security code can be sent to and stored in (R) AN 120. After completing authentication procedure 703, AMF 435 sends a response 701c to SMF.
[0078] Another alternative implementation of authentication procedure 703 is that AMF 435 first receives the MB session request at step 701a of UE 110. Before forwarding the MB session request at step 701a to SMF 436, AMF 435 can send a request to AUSF 432 to perform authentication. The AUSF 432 performs the 703 authentication procedure. The AUSF 432 can generate a security code for secure communication via the radio interface. The detailed procedure is similar to that described in step 4.2.2.2.2, “General Record” procedure of 3GPP TS 23.502. After the 703 authentication procedure has ended, AMF 435 forwards the MB Session Establishment Request message from UE 110 to SMF 436. Steps 701 b and 701 c are not necessary in such a modality.
[0079] Whether the SMF provided the information to identify the UE MB session request in step 701 b, and whether the security information
Petition 870190077600, of 8/12/2019, p. 51/69
32/41 to encrypt and decrypt the contents of the MB session are not available on the AUSF, in step 704 there will be an exchange of MB session security information in step 704 between the AUSF 432 and an SF 742 security function. the SF 742 security function can be instantiated as a central network function where security codes for encoding / decoding content generated and / or stored within the central network. In the modalities illustrated in Figures 5, 6 and 8, SF 742 can be integrated SF 542.
[0080] An alternative implementation of step 704 is that SMF 436 can communicate with MF 741, directly or indirectly via NEF 434, to obtain the security code for data encoding and decoding. SMF 436 can provide MF 741 with the information to identify the UE 110 such as GPSI, the information to identify the UE group (such as External Group Identifier), content information, an MB Session Identifier.
[0081] SMF 436 can send in step 706a an MB authorization request for session signature information to UDM 433. SMF 436 can include in the MB authorization request a EU ID (for example, SUPI), DNN , MB Session ID, PDU Session Type, content information, Information Group ID, and SMF ID. UDM 433 can communicate with member role 741 to authorize the MB session in step 706b. UDM 433 can include information to identify UE 110 such as GPSI, information to identify UE group (such as Internal Group ID or External Group ID), content information, an MB Session Identifier. The exchange of messages between UDM 433 and MF 741 can be sent directly or indirectly through an NEF 434. The NEF 434 can perform some translation of information, for example, replacing the Internal Group ID with External Group ID). In some modalities,
Petition 870190077600, of 8/12/2019, p. 52/69
33/41 the member function 741 can be instantiated as a central network function with subscription information stored within the central network, but provided by the mobile network operator or the content provider. In the modalities illustrated in Figures 5, 7 and 8, MF 741 can be integrated MF 541a, and message exchange in step 706a may involve internal signaling, and may not be necessary if UDM 433 is configured with MBMS signature information . In other modalities, MF 741 is located outside the CN, for example, MF 441 from BM-SC, in which case the message exchange 706a may involve NEF 434. LJDM 433 then sends the MB 706c authorization session to SMF 436 .
[0082] SMF 436 can then request AUSF 432 for security codes for multicast content in step 706d. Step 706d occurs if SMF 435 does not have security codes on the multicast content of an existing MB session, or if new security codes are needed for an existing MB session. SMF 436 may include information for AUSF 432 to identify the service requested by the UE, for example, content information (such as a TV channel identifier, a content identifier (such as a movie name)), a MB Session Identifier, an UE identifier (for example, SUPI and / or 5G GPSI), Internal UE Group.
[0083] In response to request from SMF 436 in step 706d, if the security information for encrypting and decrypting the MB session content is not available on the AUSF, an MB 708 session security information exchange will take place between the AUSF 432 and an SF 742 security function. AUSF 432 can send SF 742 some information that identifies the service that the UE requests, for example, content information (such as a TV channel identifier, a content identifier (such as a movie name)), an MB Session Identifier, an UE identifier (for example, 5G GPSI),
Petition 870190077600, of 8/12/2019, p. 53/69
34/41 a group identifier. In some modalities, the SF 742 security function can be instantiated as a central network function, in which security codes for content encryption / decryption are generated and / or stored in the central network; in which case step 708 can be an internal communication within AUSF 432. In the modalities illustrated in Figures 5, 6 and 8, SF 742 can be integrated SF 542.
[0084] AUSF 432 sends in step 710 the decoding code towards the EU request. It should be noted that this can be done in several ways. For example, AUSF 432 can send the decoding code to AMF 435 for forwarding to the UE. As another example, AUSF 432 can send the decoding code to SMF 436 which it then sends to AMF 435 for forwarding to the UE.
[0085] As an alternative, SMF 436 can store the existing decryption code of the MB session; steps 706d and 708 may not be necessary. The SMF 436 can send the decryption code stored locally to be sent to the UE 110.
[0086] UPF 431 can perform some processing of local content, such as video transcoding. UPF 431 may need to decode content received from a content provider or BM-SC and encode processed content before sending towards UE 110. In this case, AUSF 432 may send security codes to decode and encode content to UPF 431 through SMF 436 in step 715. Alternatively, SMF 436 can store decoding and encoding codes locally; the SMF 436 can send the locally stored decoding and encoding codes to UPF 431. The message in step 715 from SMF 436 to UPF 431 can further include MB Session ID, and content information.
[0087] After step 710, MBMS content can be sent in step 720 of CF 731, or BM-SC (not shown), or provider
Petition 870190077600, of 8/12/2019, p. 54/69
35/41 content (not shown), or other function, to UPF 431 which forwards content in step 730 towards UEs 110. In some modalities, the UPF receives the AUSF 432 coding codes as part of step 715. A UPF 431 receives in step 720 the contents of a cache function (CF 731). In some embodiments, the CF 731 can be an external function, such as the SAF 445 of the BM-SC 440 as illustrated in Figures 4-7. In some embodiments, the CF 731 can be integrated within the UPF (for example, UPF 831 in Figure 8). UPF 431 encodes the received content using the encoding codes to produce the encoded content 730 transmits the encoded content towards the plurality of UEs through one or more Radio Access Network (RAN) nodes. In some modalities, step 730 involves multicasting the content to a plurality of RAN nodes, for routing to a plurality of UEs. In some embodiments, step 730 involves transmitting the content to a plurality of RAN nodes associated with the plurality of UEs.
[0088] Figure 11 illustrates, in a block diagram, an example of a server 1100 located in the subnet that implements a network function described above in Figures 4 to 8. The server 1100 comprises an operating system 1110, a module network function 1120, which implements a network function described above in Figures 4 to 8 and other 1130 modules used by the 1100 server for other purposes. The network function implemented in the network function module 1110 can be any of the network functions shown in Figures 4 to 8, above. For example, MRMF 425 can be implemented on a corresponding 1100 server on an AN 430 (R) subarchitecture network. [0089] Figure 12 illustrates, in a block diagram, a 1200 computer system that can be used to implement some of the devices and methods disclosed here. Specific devices can use all components shown or only a subset
Petition 870190077600, of 8/12/2019, p. 55/69
36/41 of the components, and the levels of integration may vary from device to device. In addition, a device can contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. Computing system 1200 includes a processing unit 1202. Processing unit 1202 includes a central processing unit (CPU). 1214, memory 1208, and may further include a mass storage device 1204, a video adapter 1210 and an I / O interface 1212 connected to a 1220 bus.
[0090] The 1220 bus can be one or more of any type of various bus architectures, including a memory bus or memory controller, a peripheral bus or a video bus. CPU 1214 can comprise any type of electronic data processor. Memory 1208 can comprise any type of non-transitory system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM) or a combination of themselves. Memory 1208 can include ROM for use at startup, and DRAM for storing programs and data for use while running programs.
[0091] Mass storage 1204 can comprise any type of non-transitory storage device configured to store data, programs and other information and to make data, programs and other information accessible via the 1220 bus. Mass storage 1204 can comprise , for example, one or more of a solid state drive, hard disk drive, magnetic disk drive, or optical disk drive.
[0092] The 1210 video adapter and the 1212 I / O interface provide interfaces for attaching external input and output devices to the
Petition 870190077600, of 8/12/2019, p. 56/69
37/41 processing unit 1202. As illustrated, examples of input and output devices include a monitor 1118 attached to the video adapter 1210 and a mouse / keyboard / printer 1216 attached to the I / O interface 1212. Other devices can be attached to processing unit 1202, and more or less interface cards can be used. For example, a serial interface such as the universal serial bus (USB) (not shown) can be used to provide an interface for an external device.
[0093] Processing unit 1202 may also include one or more network interfaces 1206, which may comprise wired connections, such as an Ethernet cable, and / or wireless connections to access different nodes or networks. Network interfaces 1206 allow processing unit 1202 to communicate with remote units over networks. For example, network interfaces 1206 can provide wireless communication through one or more transmitters / transmit antennas and one or more receivers / receive antennas. Processing unit 1202 can be coupled to a local area network 1222 or to a wide area network for data processing and communications with remote devices, such as other processing units, the Internet or remote storage facilities.
[0094] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as would normally be understood by a person skilled in the art to which this invention belongs.
[0095] Through the descriptions of the previous modalities, the present invention can be implemented using only hardware or using software and a necessary universal hardware platform. Based on these understandings, the technical solution of the present invention
Petition 870190077600, of 8/12/2019, p. 57/69
38/41 tion can be incorporated in the form of a software product. The software product can be stored on a non-volatile or non-transitory storage medium, which can be a CD-ROM, USB flash disk or a removable hard disk. The software product includes a number of instructions that allow a computer device (personal computer, server or network device) to perform the methods provided in the modalities of the present invention. For example, such an execution may correspond to a simulation of logical operations as described here. The software product may additionally or alternatively include a number of instructions that allow a computer device to perform operations to configure or program a digital logic apparatus in accordance with modalities of the present invention.
[0096] Other embodiments of the present invention are provided below. It should be noted that the numbering used in the following section does not necessarily have to comply with the numbering used in the previous sections.
[0097] Mode 1: A network architecture comprising:
the central network (CN) comprising an authentication server function (AUSF) and the network exposure function (NEF) communicably connected via the NG AUSF-NEF interface; and a broadcast-multicast service center (BM-SC) comprising a security function communicated to the NEF through an NG MBMS-NEF interface.
[0098] Mode 2: A network architecture comprising: a central network (CN) comprising an authentication server function (AUSF), a network exposure function (NEF) and a policy control function (PCF), AUSF and NEF communicably connected via an NG interface AUSF-NEF, NEF and PCF communicated via an NG interface
Petition 870190077600, of 8/12/2019, p. 58/69
39/41
PCF-NEF; and a broadcast-multicast service center (BM-SC) comprising a member function, the member function communicated to the NEF via an NG MBMS-NEF interface, and the member function communicated to the PCF via an interface NG5.
[0099] Mode 3: The network architecture comprising:
a central network (CN) comprising an authentication server function (AUSF), a network exposure function (NEF) and a policy control function (PCF), AUSF and NEF communicably connected via an NG AUSF interface -NEF, NEF and PCF communicably connected via an NG PCF-NEF interface; and a broadcast-multicast service center (BM-SC) comprising a member function and a security function;
wherein the member function communicably connected to the NEF via an NG MBMS-NEF interface, and the member function communicated to the PCF via an NG5 (QoS) interface; and where the safety function communicates to the NEF via an NG MBMS-NEF interface.
[00100] Mode 4: A network architecture comprising:
a broadcast-multicast service center (BM-SC) comprising a transport and proxy function, a service announcement function and a session and broadcast function communicably connected to each of the transport and proxy function and the announcement function. service; and a central network comprising a flat user function (UPF) communicably connected to the transport and proxy function
Petition 870190077600, of 8/12/2019, p. 59/69
40/41 via a first NG6-MBMS interface and communicably connected to the service announcement function via a second NG6-MBMS interface;
in which a transmission from the multicast and broadcast multimedia subsystem (MBMS) received in the session and transmission function is forwarded to the transport and proxy function, then forwarded by the NG6-MBMS interface to the UPF, then forwarded to an access node (AN ) via an NG3-MBMS interface.
[00101] Mode 5: A method to provide access to a broadcast from the multicast and broadcast multimedia subsystem (MBMS), the method comprising an authentication server (AUSF) function on a central network (CN):
receive a security code from a multicast and broadcast multimedia subsystem security function (MBMS) from a broadcast-multicast service center (BM-SC), the security code received from a network exposure function (NEF ) through an NG AUSF-NEF interface, NEF having received the security code from the MBMS security function through an NG MBMS-NEF interface; and send the security code to user request equipment.
[00102] Mode 6: A method for transmitting a secure transmission from the multicast and broadcast multimedia subsystem (MBMS), the method comprising a function of the authentication server (AUSF):
send a first security code (UPF) to a first security code to decode an MBMS transmission requested by the user's equipment (UE) received at the UPF via an NG6-MBMS interface; and
Petition 870190077600, of 8/12/2019, p. 60/69
41/41 send the second security code to the UPF to encode the transmission of MBMS to be sent to an access network (AN) through an N3-MBMS interface, the UE connected to the AN.
[00103] Although the present invention has been described with reference to specific characteristics and modalities thereof, it is evident that various modifications and combinations can be made without departing from the invention. The specification and drawings are, therefore, considered simply as an illustration of the invention as defined by the appended claims, and are contemplated to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present invention.

权利要求:
Claims (20)
[1]
1. Method for delivering content from a content provider to a plurality of User Equipment UEs (110) using at least one of a multicast and broadcast data transmission, the method characterized by:
receive, via a function from the AUSF authentication server (432; 532) of a central CN network (130; 430; 530; 630; 730; 830), a request for an authenticated UE (110) to access content directed to the plurality of UEs (110);
receive, via AUSF (432, 532) from the CN (130; 430; 530; 630; 730; 830), security information comprising a security function decoding code that provides the decoding code for use by the UE (110 ) authenticated to decode the content; and send, through AUSF (432, 532) of the CN (130, 430, 530, 630, 730, 830), the decryption code towards the authenticated UE (110).
[2]
2. Method, according to claim 1, characterized by the fact that sending the decryption code towards the authenticated UE (110) comprises sending the decoding code to an AMF (435) access and mobility management function for forwarding to the authenticated UE (110).
[3]
3. Method, according to claim 1, characterized by the fact that sending the decryption code towards the authenticated UE (110) comprises sending the decoding code to an SMF Session Management Function (436) for forwarding to the UE (110) authenticated through an AMF mobility and access management function (435).
[4]
Method according to claim 1, further characterized by:
Petition 870190077604, of 12/08/2019, p. 9/13
2/5 send, via AUSF (432; 532) from the CN (130; 430; 530; 630; 730; 830), to a SMF Session Management Function (436) a second decoding code for use by a UPF User Plan (431; 831) in decoding the content received by UPF (431; 831) from the content provider, the content received directed to the plurality of UEs (110); and send, via AUSF (432; 532) from the CN (130; 430; 530; 630; 730; 830), to SMF (436) a first security code for use by the UPF (431; 831) when encoding the requested content for routing towards the plurality of UEs (110), the first security code corresponding to the decryption code.
[5]
5. Method according to any one of claims 1 to 4, characterized by the fact that the safety function is at least one of:
instantiated as a central network function with the security information generated and stored within the CN (130; 430; 530; 630; 730; 830); and located external to the central network (130; 430; 530; 630; 730; 830).
[6]
6. Method according to any one of claims 1 to 5, characterized by the fact that the safety information is received via another central network function.
[7]
7. Method for establishing a session to deliver content to a plurality of EU User Equipment (110) using at least one of a multicast and broadcast data transmission, the method characterized by:
receive, through an SMF Session Management Function (436) from a central CN network (130; 430; 530; 630; 730; 830), a request for an authenticated UE (110) to access content targeting the plurality of UEs ( 110);
Petition 870190077604, of 12/08/2019, p. 10/13
3/5 request, by CN's SMF (436) (130; 430; 530; 630; 730; 830), authorization of a UDM (433; 533) unified data management function from CN (130; 430; 530; 630,730,830) which is configured to receive information from members of a member role; and initiate, by the SMF (436) of the CN (130; 430; 530; 630; 730; 830), the transmission of a decoding code towards the UE (110).
[8]
8. Method, according to claim 7, characterized by the fact that the member function is at least one among:
instantiated as a central network function with member information stored within the central network (130; 430; 530; 630; 730; 830), but provided by the content provider;
located external to the central network (130; 430; 530; 630; 730; 830).
[9]
9. Method, according to claim 7, characterized by the fact that member information is received through another central network function.
[10]
Method according to any one of claims 7 to 9, further characterized by:
after receiving the request, forward, through the CN SMF (130; 430; 530; 630; 730; 830), the request to a function of the AUSF authentication server (432; 532) of a central CN network (130; 430; 530; 630; 730; 830) to authenticate the UE (110).
[11]
11. Method according to any one of claims 7 to 10, characterized in that the SMF (436) of the CN (130; 430; 530; 630; 730; 830) initiates the transmission of a decoding code towards the UE (110) comprises at least one of:
transmit, by the SMF (436) of the CN (130; 430; 530; 630; 730; 830), a decoding code previously stored towards the UE (110); and request, through the SMF (436) of the CN (130; 430; 530; 630; 730;
Petition 870190077604, of 12/08/2019, p. 11/13
4/5
830), the decoding code of a function of the AUSF authentication server (432; 532) of the central network CN (130; 430; 530; 630; 730; 830).
[12]
12. Method for delivering content from a content provider to a plurality of user equipment, UEs (110), the method performed by a flat user function UPF (431; 831) from a central CN network (130; 430; 530 ; 630; 730; 830), the method characterized by:
receive, by UPF (431, 831) from the CN (130; 430; 530; 630; 730; 830), content provided by the content provider to the plurality of UEs (110);
store, by UPF (431, 831) of the CN (130, 430, 530, 630, 730, 830), the content in a cache function;
receive, by UPF (431, 831) from the CN (130; 430; 530; 630; 730; 830), a code encoding a function of the AUSF authentication server (432; 532);
receive the contents of the cache function;
encode, by UPF (431, 831) of CN (130, 430, 530, 630, 730, 830), the content received using the encoding code to produce encoded content; and transmit, by UPF (431, 831) of the CN (130; 430; 530; 630; 730, 830), the encoded content towards the plurality of UEs (110) through at least one Radio Access Network node RAN.
[13]
13. Method, according to claim 12, characterized by the fact that the transmission, by UPF (431; 831) of the CN (130; 430; 530; 630; 730, 830), comprises the encoded content encoded content to each of at least one RAN node.
[14]
14. Method, according to claim 12, characterized by the fact that the transmission, by UPF (431; 831) of the CN (130; 430; 530; 630; 730, 830), of the encoded content comprises transmitting the
Petition 870190077604, of 12/08/2019, p. 12/13
5/5 coded content for each of at least one RAN node.
[15]
15. Method according to any one of claims 12 to 14, characterized in that the cache function is a central network cache function.
[16]
16. Method according to any one of claims 12 to 15, characterized by the fact that the UPF (431; 831) is configured to support multicast and broadcast data distribution to multiple RAN nodes and receive the contents of a function cache comprises receiving content over an interface.
[17]
17. Method according to claim 16, characterized by the fact that transmitting the encoded content towards the plurality of UEs (110) comprises transmitting the encoded content using an interface.
[18]
18. Function of the AUSF authentication server (432; 532) of a central CN network (130; 430; 530; 630; 730; 830) characterized by the fact that it is configured to perform the method, as defined in any of the claims 1 to 6.
[19]
19. Flat function of the UPF user (431; 831) of a central CN network (130; 430; 530; 630; 730; 830) characterized by the fact that it is configured to perform the method as defined in any of claims 12 to 17.
[20]
20. Session management function, SMF, (436) of a central network, CN, (130; 430; 530; 630; 730; 830) characterized by the fact that it is configured to perform the method, as defined in any one claims 7 to 11.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019013865A2|2020-04-14|network architecture having multicast and broadcast multimedia subsystem capabilities

---

JP5259637B2|2013-08-07|Method and apparatus for broadcast application in a wireless communication system

---

JP5295224B2|2013-09-18|Method and apparatus for providing multimedia broadcast multicasting service

---

US7995510B2|2011-08-09|Method for implementing broadcast/multicast area management in a wireless communication system

---

WO2017016326A1|2017-02-02|Data transmission method for edge mbms service and relevant device

---

US20080253322A1|2008-10-16|WiMAX Multicast Broadcast Network System Architecture

---

US9503865B2|2016-11-22|Providing multiple multicast streams over a single transport bearer channel

---

EP3607774B1|2020-09-30|Methods and apparatuses for selecting a session management entity for serving a wireless communication device

---

JP6251732B2|2017-12-20|Centralized key management in EMBMS

---

US10972447B2|2021-04-06|Short message service gateway for media streaming security

---

US20200195981A1|2020-06-18|Method and system for carrier-initiated traffic tuning and communication of subscriber parameters

---

WO2022027696A1|2022-02-10|Method and apparatus for configuring security information

---

WO2021189933A1|2021-09-30|Method, apparatus and system for configuring radio bearer

---

ES2354428T3|2011-03-14|PROCEDURE AND APPLIANCE FOR APPLICATION OF DISSEMINATION IN A WIRELESS COMMUNICATION SYSTEM.

---

WO2022027476A1|2022-02-10|Key management method and communication apparatus

---

KR101002829B1|2010-12-21|Method for protecting mbms service data in multimedia broadcast/multicast service system

---

WO2021238280A1|2021-12-02|Communication method, apparatus and system

---

US20150334561A1|2015-11-19|Method, wireless device, computer program and computer program product for assisting access to access protected services

同族专利:

---

公开号 | 公开日

---

US10779163B2|2020-09-15|

---

CN110169104B|2020-10-09|

---

WO2018127108A1|2018-07-12|

---

CN112367624A|2021-02-12|

---

US20210051474A1|2021-02-18|

---

CN110169104A|2019-08-23|

---

US20180192289A1|2018-07-05|

---

EP3556128A1|2019-10-23|

---

EP3556128A4|2019-10-23|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US7349412B1|2002-12-20|2008-03-25|Sprint Spectrum L.P.|Method and system for distribution of voice communication service via a wireless local area network|

---

US20040128259A1|2002-12-31|2004-07-01|Blakeley Douglas Burnette|Method for ensuring privacy in electronic transactions with session key blocks|

---

EP1811736A1|2006-01-18|2007-07-25|Matsushita Electric Industrial Co., Ltd.|Providing service data of a bidirectional service by using a downlink multicast service |

---

CN100596068C|2006-06-23|2010-03-24|东南大学|Safety multicast method based on protocol of conversation initialization|

---

CN101582730B|2008-05-15|2011-06-01|华为技术有限公司|Method, system, corresponding device and communication terminal for providing MBMS service|

---

US8938749B2|2010-08-31|2015-01-20|At&T Intellectual Property I, L.P.|System and method to troubleshoot a set top box device|

---

US9467285B2|2010-09-07|2016-10-11|Nokia Technologies Oy|Security of a multimedia stream|

---

US9306759B2|2013-08-28|2016-04-05|Cellco Partnership|Ultra high-fidelity content delivery using a mobile device as a media gateway|

---

US9319230B2|2014-02-10|2016-04-19|Verizon Patent And Licensing Inc.|Providing multiple multicast streams over a single transport bearer channel|

---

KR20160117121A|2015-03-31|2016-10-10|삼성전자주식회사|Method and apparatus for peak to average power reduction in wireless communication systems using spectral mask filling|

---

WO2016033474A1|2014-08-28|2016-03-03|Interdigital Patent Holdings, Inc.|Method and apparatus for capture caching|

---

WO2016072814A1|2014-11-07|2016-05-12|Samsung Electronics Co., Ltd.|Method and apparatus for transmitting group message to user equipment |

---

WO2017037193A1|2015-09-02|2017-03-09|Telefonaktiebolaget Lm Ericsson |Methods and network nodes for scalable top-of-chain selection in mobile service chaining|

---

WO2017157458A1|2016-03-18|2017-09-21|Telefonaktiebolaget Lm Ericsson |Methods, apparatuses and computer program products for content distribution|

---

US10362511B2|2016-05-17|2019-07-23|Lg Electronics Inc.|Method and apparatus for determining PDU session identity in wireless communication system|

---

US10278156B2|2016-09-19|2019-04-30|At&T Intellectual Property I, L.P.|Streaming media cellular broadcast|

---

EP3523924A1|2016-10-06|2019-08-14|Convida Wireless, LLC|Session management with relaying and charging for indirect connection for internet of things appplications in 3gpp network|US10251147B2|2017-03-20|2019-04-02|Samsung Electronics Co., Ltd.|Method for supporting efficient PDU session activation and deactivation in cellular networks|

---

KR20180106804A|2017-03-20|2018-10-01|삼성전자주식회사|A method for supporting efficient pdu session activation and deactivation in cellular networks|

---

EP3589062B1|2017-03-21|2021-05-12|Huawei Technologies Co., Ltd.|Communication method and apparatus|

---

US11039497B2|2017-09-18|2021-06-15|Qualcomm Incorporated|User plane based small data service|

---

US11109277B2|2017-11-20|2021-08-31|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Service configuration method and related product|

---

CN110740149B|2018-07-19|2021-04-09|华为技术有限公司|Communication method and device|

---

CN110891269A|2018-09-10|2020-03-17|华为技术有限公司|Data protection method, equipment and system|

---

CN111757283A|2019-03-29|2020-10-09|华为技术有限公司|Charging method and device|

---

CN112866931A|2019-06-17|2021-05-28|腾讯科技（深圳）有限公司|Virtual network group broadcasting method, device, equipment and system|

---

US20210067960A1|2019-08-26|2021-03-04|Qualcomm Incorporated|5g broadcast/multicast security key refresh|

---

WO2021163260A1|2020-02-13|2021-08-19|Convida Wireless, Llc|Methods of delivery mode switch for multicast and broadcast service in a 5g network|

---

WO2021165760A1|2020-02-21|2021-08-26|Telefonaktiebolaget Lm Ericsson |Authentication server function selection in authentication and key management|

---

CN111526552A|2020-05-13|2020-08-11|腾讯科技（深圳）有限公司|UE execution method and UE, SMF entity execution method and SMF entity|

---

WO2021237526A1|2020-05-27|2021-12-02|Mediatek Singapore Pte. Ltd.|Methods and apparatus of rlc based reliable multicast transmission|

---

CN111818521A|2020-06-14|2020-10-23|苏州浪潮智能科技有限公司|Authority authentication method and system based on data center 5G network encryption multicast|

---

WO2022027696A1|2020-08-07|2022-02-10|华为技术有限公司|Method and apparatus for configuring security information|

---

CN114079872A|2020-08-13|2022-02-22|华为技术有限公司|Method and communication device for authentication|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762442644P| true| 2017-01-05|2017-01-05|

---

US15/861,096|US10779163B2|2017-01-05|2018-01-03|Network architecture having multicast and broadcast multimedia subsystem capabilities|

---

PCT/CN2018/071461|WO2018127108A1|2017-01-05|2018-01-04|Network architecture having multicast and broadcast multimedia subsystem capabilities|

---